Skip to content
This repository has been archived by the owner on Sep 22, 2023. It is now read-only.

Format Guide | Fix Guides section #963

Merged
merged 1 commit into from
Sep 7, 2023
Merged

Conversation

markzegarelli
Copy link
Contributor

Amplitude Developer Docs PR

Description

Fixed a fenced code block that escaped its bounds

Deadline

When do these changes need to be live on the site?

Change type

  • Doc bug fix. Fixes #[insert issue number]. Amplitude contributors include Jira issue number.
  • Doc update.
  • New documentation.
  • Non-documentation related fix or update.

PR checklist:

  • My documentation follows the style guidelines of this project.
  • I previewed my documentation on a local server using mkdocs serve.
  • Running mkdocs serve didn't generate any failures.
  • I have performed a self-review of my own documentation.

@amplitude-dev-docs

@github-actions
Copy link

github-actions bot commented Sep 7, 2023

🦙 MegaLinter status: ❌ ERROR

Descriptor Linter Files Fixed Errors Elapsed time
❌ MARKDOWN markdownlint 1 14 0.39s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

@aws-amplify-us-east-1
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-963.d19s7xzcva2mw3.amplifyapp.com

@markzegarelli markzegarelli merged commit d14d951 into main Sep 7, 2023
2 of 4 checks passed
@markzegarelli markzegarelli deleted the format-guide-fixes branch September 7, 2023 17:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant